packages/react-core/src/components/Page/PageGroup.tsx (1)

57-62: ⚡ Quick win

Consider adding a dev warning when isStickyStuck is set without stickyBase

Both components already follow the pattern of warning via useEffect when a prop combination is a silent no-op (e.g., hasOverflowScroll + no aria-label). isStickyStuck=true without stickyBase applies no CSS classes — a console warning would surface this misconfiguration consistently.

💡 Suggested addition (mirroring the existing pattern)

  useEffect(() => {
    if (hasOverflowScroll && !ariaLabel) {
      /* eslint-disable no-console */
      console.warn('PageGroup: An accessible aria-label is required when hasOverflowScroll is set to true.');
    }
+   if (isStickyStuck && !stickyBase) {
+     /* eslint-disable no-console */
+     console.warn('PageGroup: isStickyStuck has no effect without stickyBase also being set.');
+   }
- }, [hasOverflowScroll, ariaLabel]);
+ }, [hasOverflowScroll, ariaLabel, isStickyStuck, stickyBase]);

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@packages/react-core/src/components/Page/PageGroup.tsx` around lines 57 - 62,
The component should emit a dev-time console warning when isStickyStuck is true
but stickyBase is not provided because that prop combination is a silent no-op;
inside the existing useEffect block in PageGroup (or a nearby useEffect that
watches prop combos), add a check for isStickyStuck && !stickyBase and call
console.warn with a clear message (e.g., "PageGroup: isStickyStuck is set to
true but stickyBase is not provided — this will have no effect.") so developers
see the misconfiguration; reference the isStickyStuck and stickyBase props and
ensure the effect depends on [isStickyStuck, stickyBase].

packages/react-core/src/components/Page/PageSection.tsx (1)

117-122: ⚡ Quick win

Same isStickyStuck without stickyBase warning applies here.

Same as PageGroup — consider adding a console.warn inside the existing useEffect when isStickyStuck && !stickyBase to keep the DX pattern consistent across both components.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@packages/react-core/src/components/Page/PageSection.tsx` around lines 117 -
122, In PageSection's useEffect add the same developer experience warning as
PageGroup: when isStickyStuck is true and stickyBase is falsy, call console.warn
to inform developers to provide stickyBase; update the existing effect that
currently checks hasOverflowScroll and ariaLabel (function/component:
PageSection, hook: useEffect, props/vars: hasOverflowScroll, ariaLabel,
isStickyStuck, stickyBase) to also perform a conditional console.warn for
isStickyStuck && !stickyBase so the pattern is consistent across components.